⚠️ Unpublished: This item is from a solution that is not yet published on Azure Marketplace or not installed in Content Hub.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊
| Attribute | Value |
|---|---|
| Publisher | Beyond Security |
| Support Tier | Partner |
| Support Link | https://beyondsecurity.freshdesk.com/support/home |
| Categories | domains |
| Version | 2.0.0 |
| Author | Beyond Security - isv@email.com |
| First Published | 2022-05-02 |
| Solution Folder | Beyond Security beSECURE |
The Beyond Security beSECURE Solution for Microsoft Sentinel allows you to easily connect your Beyond Security beSECURE scan events, scan results and audit trail with Microsoft Sentinel, to view dashboards, create custom alerts, and improve investigation. This gives you more insight into your organization's network and improves your security operation capabilities.
**Underlying Microsoft Technologies used: **
This solution takes a dependency on the following technologies, and some of these dependencies either may be in Preview state or might result in additional ingestion or operational costs:
a. Azure Monitor HTTP Data Collector API
This solution has 1 discovered data connector(s)⚠️ (not in Solution definition):
🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.
🔶 CLv1: This connector ingests into a table that uses the legacy Custom Log V1 schema format with type-suffixed column names (e.g.
_s,_d,_b,_t,_g). Note: identification is based on column name suffixes which are also permitted in CLv2, so this classification may not always be accurate.
This solution uses 3 table(s):
| Table | Used By Connectors | Used By Content |
|---|---|---|
beSECURE_Audit_CL 🔶 |
Beyond Security beSECURE | - |
beSECURE_ScanEvent_CL 🔶 |
Beyond Security beSECURE | - |
beSECURE_ScanResults_CL 🔶 |
Beyond Security beSECURE | - |
🔶 CLv1: This table uses the legacy Custom Log V1 schema format with type-suffixed column names (e.g.
_s,_d,_b,_t,_g). Note: identification is based on column name suffixes which are also permitted in CLv2, so this classification may not always be accurate.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊